Gameplay in a Chat Thread

ABSTRACT

There is provided a system and method for user generated gameplay in chat. The system including a memory storing a text and multimedia messaging software application, and a processor configured to execute the text and multimedia messaging software application to initiate a message exchange session with a remote mobile device, in response to a request received from a user of the mobile device, the message exchange session displaying a user interface for exchanging text and multimedia messages, provide a plurality of games for selection by the user to be played during the message exchange session and within the user interface for exchanging text and multimedia messages, receive a selection of one of the plurality of games by the user after initiating the message exchange session, and initiate the one of the plurality of games for playing within the user interface for exchanging text and multimedia messages.

BACKGROUND

Nowadays, users of mobile devices are able to chat with their friendsand family using various messaging applications. When chatting withfriends and family, these users are able to send chat messages,pictures, and movies. However, users of these current messagingapplications may find it boring to only be able to send chat messages,pictures, and movies to friends and family. For example, a user may wantto play games with his or her friends and family. This can cause aproblem since it requires the user to exit out of his or her messagingapplication to launch a gaming software application that is directedtowards a game. Furthermore, this also requires the friends and familyof that user to also have the same gaming software application installedon their own mobile device in order to play with the user.

SUMMARY

The present disclosure is directed to a system and method for gameplayin a chat thread, substantially as shown in and/or described inconnection with at least one of the figures, as set forth morecompletely in the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 presents a system for integrating gameplay in a chat thread,according to one implementation of the present disclosure.

FIG. 2 presents an example of user generated gameplay levels in a chatthread, according to one implementation of the present disclosure.

FIG. 3 shows a flowchart illustrating a method for generating usergenerated gameplay levels in a chat thread, according to oneimplementation of the present disclosure.

FIG. 4A presents a first example of integrating game mechanics in a chatthread, according to one implementation of the present disclosure.

FIG. 4B presents a second example of integrating game mechanics in achat thread, according to one implementation of the present disclosure.

FIG. 5 shows a flowchart illustrating a method for integrating gamemechanics in a chat thread, according to one implementation of thepresent disclosure.

FIG. 6 presents an example of chat message gameplay scripting, accordingto one implementation of the present disclosure.

FIG. 7 shows a flowchart illustrating a method for chat message gameplayscripting, according to one implementation of the present disclosure.

FIG. 8 presents an example of chat based trading with limited timemechanics, according to one implementation of the present disclosure.

FIG. 9 shows a flowchart illustrating a method for chat based tradingwith limited time mechanics, according to one implementation of thepresent disclosure.

FIG. 10 presents an example of a multi modal integrated Avatar emoji,according to one implementation of the present disclosure.

FIG. 11 shows a flowchart illustrating a method for using a multi modalintegrated Avatar emoji, according to one implementation of the presentdisclosure.

DETAILED DESCRIPTION

The following description contains specific information pertaining toimplementations in the present disclosure. The drawings in the presentapplication and their accompanying detailed description are directed tomerely exemplary implementations. Unless noted otherwise, like orcorresponding elements among the figures may be indicated by like orcorresponding reference numerals. Moreover, the drawings andillustrations in the present application are generally not to scale, andare not intended to correspond to actual relative dimensions.

FIG. 1 presents a system for integrating game mechanics in a chatthread, according to one implementation of the present disclosure.System 100 of FIG. 1 includes user 101 in possession of mobile device110, and user 102 in possession of mobile device 150. Mobile device 110includes processor 111, display 112, input interface 113, communicationinterface 114, and memory 115. Memory 115 includes messaging softwareapplication 120 and game software application 130. Messaging softwareapplication 120 includes message stream 121, keyboard 126, and gameselection 127. Message stream 121 includes chat bubbles 122, game launch123, game objects 124, and user input 125. Game software application 130includes games 131, objects 132, and avatars 133. Mobile device 150includes processor 151, display 152, input interface 153, communicationinterface 154, and memory 155. Memory 155 includes messaging application160 and game software application 130. Messaging application 160includes message stream 121, keyboard 166, and game selection 127.Message stream 121 includes chat bubbles 122, game launch 123, gameobjects 124, and user input 165. System 100 of FIG. 1 further includesgame request 170, game acceptance 171, and game moves 172.

Mobile device 110 may comprise a mobile phone, a tablet, a personalcomputer, or any other device capable of executing a messaging softwareapplication to communicate with other mobile devices. As shown in FIG.1, mobile device 110 includes display 112 and input interface 113. Inputinterface 113 may comprise, for example, a keyboard, a mouse, a gamecontroller, a touch-screen input, a thermal and/or electrical sensor, orany other device capable of accepting user input for use with mobiledevice 110. Display 112 may comprise a liquid crystal display (LCD)screen built into mobile device 110. In alternative implementations ofthe present disclosure, display 112 may be another type of displayhardware, such as cathode-ray tubes (CRT) monitors. In yet otherimplementations, display 112 may also be touch sensitive and may serveas input interface 113.

Mobile device 110 further includes processor 111 and memory 115.Processor 111 may be configured to access memory 115 to store receivedinput or to execute commands, processes, or programs stored in memory115, such as messaging software application 120 and game softwareapplication 130. Processor 111 may correspond to a processing device,such as a microprocessor or similar hardware processing device, or aplurality of hardware devices. However, in other implementationsprocessor 111 refers to a general processor capable of performing thefunctions required of mobile device 110. Memory 115 is a sufficientmemory capable of storing commands, processes, and programs forexecution by processor 111. Memory 115 may be instituted as ROM, RAM,flash memory, or any sufficient memory capable of storing a set ofcommands. In other implementations, memory 115 may correspond to aplurality memory types or modules.

Also illustrated in FIG. 1, mobile device 110 further includescommunication interface 114. In the implementation of FIG. 1,communication interface 114 includes any device that is capable bothtransmitting data with a transmitter and receiving data with a receiver.Processor 111 of mobile device 110 is thus configured to controlcommunication interface 114 to communicate with other mobile devices,such as mobile device 150.

It should be noted that mobile device 150, processor 151, display 152,input interface 153, communication interface 154, and memory 155 may besimilar to mobile device 110, processor 111, display 112, inputinterface 113, communication interface 114, and memory 115,respectively. For example, mobile device 150 may include a mobile phone,a tablet, a personal computer, or any other device capable of executinga messaging software application to communicate with other mobiledevices. Processor 151 may be configured to access memory 155 to storereceived input or to execute commands, processes, or programs stored inmemory 155, such as messaging application 160 and game softwareapplication 130. Furthermore, processor 151 of mobile device 150 may beconfigured to control communication interface 154 to communicate withother mobile devices using any wired or wireless technology.

Also illustrated in FIG. 1, mobile device 110 includes game softwareapplication 130. Mobile device 110 may utilize game software application130 to create and play games with other mobile devices, where the gamesare created and played within a messaging application, such as messagingsoftware application 120. Messaging software application 120 may includea software application used by mobile device 110 to communicate withother mobile devices, such as mobile device 150. For example, messagingsoftware application 120 may include a short message service (SMS) usedby mobile device 110 to send and receive text and multimedia messageswith other mobile devices. As such, by utilizing game softwareapplication 130, mobile device 110 is able to allow user 101 to directlycreate and play games within messaging software application 120, thusextending the capabilities of messaging software application 120.

It should be noted that the implementation of FIG. 1 only illustratesmessaging software application 120 as being separate from game softwareapplication 130, however, the present disclosure is not limited to theimplementation of FIG. 1. For example, in other implementations,messaging software application 120 and game software application 130 maybe combined into a single software application.

As illustrated in FIG. 1, game software application 130 includes games131, objects 132, and avatars 133. Games 131 may include a list of gamesthat user 101 of mobile device 110 may select from when creating a gamewithin messaging software application 120. For example, and as will beillustrated in FIGS. 2, 4A, 4B, 6, 8, and 10, games 131 may include, butare not limited to, user generated games, shooting games, dice games,avatar games, and trading games. Objects 132 may include differentobjects that can be used by user 101 of mobile device 110 when creatingand playing one or more of games 131. For example, objects 132 mayinclude, but are not limited to, avatars, people, cars, buildings, food,animals, pictures, movie clips, or any other objects that can beutilized to create and play different games 131. Finally, avatars 133may include all of the different avatars that may be utilized by user101 of mobile device 110 when creating and playing one or more of games131.

Also illustrated in FIG. 1, messaging software application 120 includesmessage stream 121, keyboard 126, and game selection 127. Message stream121 may include an user interface used by user 101 of mobile device 110to exchange text and multimedia messages with users of other mobiledevices, such as user 102 of mobile device 150. For example, messagestream 121 may include a list of each of the messages that have beenexchanged between mobile device 110 and mobile device 150. Keyboard 126may include the keyboard used by user 101 of mobile device 110 totransmit messages within message stream 121. For example, keyboard 126may include, but is not limited to, a normal keyboard that includesletters for typing words or a special keyboard that can be used to typespecial figures, such as different emotional faces or objects. Finally,game selection 127 may include a selection button included withinmessaging software application 120 that user 101 of mobile device 110uses to select games to be created and played within message stream 121.For example, game selection 127 may allow user 101 to select one or moreof games 131 from game software application 130.

It should be noted that messaging application 160 and keyboard 166 ofmobile device 150 may be similar to messaging software application 120and keyboard 126 of mobile device 110. For example, messagingapplication 160 may include a software application used by user 102 ofmobile device 150 to communicate with users of other mobile devices,such as user 101 of mobile device 110. As such, messaging softwareapplication 120 and messaging application 160 may include the same SMS,or messaging software application 120 and messaging application 160 mayinclude different SMSs. Furthermore, keyboard 166 may be similar tokeyboard 126 except that keyboard 166 is generated specifically formessaging application 160 of mobile device 150.

Also illustrated in FIG. 1, message stream 121 includes chat bubbles122, game launch 123, game objects 124, and user input 125. Chat bubbles122 may include objects within message stream 121 that are used todistinguish between each text and multimedia message that exchangedusing message stream 121. For example, if message stream 121 includes achat stream between mobile device 110 and mobile device 150, chatbubbles 122 would distinguish between each message that is exchangedbetween mobile device 110 and mobile device 150. In such an example,chat bubbles 122 are created each time user 101 of mobile device 110transmits a message to user 102 of mobile device 150, and each time user101 of mobile device 110 receives a message from user 102 of mobiledevice 150.

Game launch 123 may include a message sent within message stream 121that either requests the starting of one of games 131, or accepts arequest of one of games 131 if mobile device 110 has already receivedthe request from another mobile device. For example, and using theexample above where message stream 121 includes an input interface forexchanging messages between mobile device 110 and mobile device 150,game launch 123 may include a game request transmitted from mobiledevice 110 to mobile device 150 within message stream 121 requesting thestart of one of games 131. For another example, and again using theexample above where message stream 121 includes an user interface forexchanging messages between mobile device 110 and mobile device 150, ifmobile device 110 has already received a game request from mobile device150, then game launch 123 may include an acceptance of the request byuser 101 of mobile device 110. In such an example, the request may bedisplayed within message stream 121 in one of chat bubbles 122.

Game objects 124 may include each of the objects that have been used tocreate and play the game within message stream 121. For example, gameobjects 124 may include one or more of objects 132, or game objects 124may include one or more of avatars 133. Finally, user input 125 mayinclude each move made by user 101 of mobile device 110 during theplaying of the game. For example, if user 101 of mobile device 110 isplaying a game with user 102 of mobile device 150, user input 125 wouldinclude each move made by user 101 of mobile device 110 during theplaying of the game, and user input 165 would include each move made byuser 102 of mobile device 150 during the playing of the game.

In the implementation of FIG. 1, user 101 of mobile device 110 may beusing messaging software application 120 to exchange text and multimediamessages with user 102 of mobile device 150, where the messages aredisplayed using chat bubbles 122 within message stream 121. During theconversation between user 101 and user 102, user 101 may decide that heor she wants to play a game with user 102. In order to play a game withuser 102, user 101 uses game selection 127 to select one of games 131,where game selection 127 was added to messaging software application 120by game software application 130. After selecting one of games 131 usinggame selection 127, mobile device 110 transmits game request 170 tomobile device 150 by posting game request 170 within message stream 121.

User 102 of mobile device 150 may receive game request 170 from user 101of mobile device 110 within message stream 121, where game request 170is displayed to user 102 within one of chat bubbles 122. User 102 maythen accept game request 170 received by user 101 and mobile device 150and may transmit game acceptance 171 to mobile device 110 in response.By accepting game request 170 from user 101 of mobile device 110, user101 of mobile device 110 and user 102 of mobile device 150 have createda game within message stream 121. User 101 and user 102 are now able toplay each other in a friendly game within message stream 121, usingvarious game moves 172 (corresponding to user input 125 and user input165). As such, user 101 is not required to download or launch a newsoftware application to play a game with user 102.

It should be noted that in some implementations, and as discussed above,display 112 may be touch sensitive and serve as input interface 113. Insuch implementations, the game may be displayed on display 112 of mobiledevice 110 and user input 125 may be made by user 101 directly touchingparts of display 112. For example, if the game is a shooting game, userinput 125 may include user 101 shooting at game objects 124 within thegame by directly touching parts of display 112 where game objects 124are located.

FIG. 2 presents an example of user generated gameplay levels in a chatthread, according to one implementation of the present disclosure. FIG.2 includes mobile device 210 and mobile device 250. Mobile device 210includes message stream 221 a, keyboard 226, and game selection 227.Message stream 221 a includes chat bubbles 222 (corresponding messagesexchanged between user 201 and user 202 within message stream 221 a),game object 224, game request 270, and game acceptance 271. Messagestream 221 a further includes messages from user 101 and user 102.Mobile device 250 includes message stream 221 b, which includes chatbubbles 222 and game object 224.

With respect to FIG. 2, it should be noted that user 201, user 202,mobile device 210, each of message stream 221 a and message stream 221b, chat bubbles 222, game object 224, keyboard 226, game selection 227,game request 271, and game acceptance 272 correspond respectively touser 101, user 102, mobile device 110, message stream 121, chat bubbles122, game objects 124, keyboard 127, game selection 127, game request170, and game acceptance 171 from FIG. 1. It should further be notedthat only one of chat bubbles 222 within message stream 221 a and one ofchat bubbles 222 within message stream 221 b is labeled for claritypurposes even though each message exchanged between user 201 and user202 is included within one of chat bubbles 222.

FIG. 2 illustrates an example of a game that can be created and playedwithin a message stream that allows users to generate play levels usingthe actual chat conversation within the message stream. Users areprovided with a game trigger that the users can activate in order toplace objects within the chat conversation. The objects are then able tointeract with the chat messages (chat bubbles) of the chat conversationbetween the users during the playing of the game. As such, users areable to design game levels through posting typical chat conversations,which include both the chat messages and the objects. This gives theusers the ability to create different game levels each time the usersdecide to play a game, since the size and types of chat messages andobjects will differ within a chat conversation each time a game isplayed within the message stream.

In the implementation of FIG. 2, mobile device 210 includes messagestream 221 a, which may correspond to a chat conversation between user201 and user 202 during the creation of a game. For example, user 201may have used game selection 227 to select a shooting game to play withuser 202, where the shooting game is created within message stream 221 ausing chat bubbles 222. To begin the game, user 201 first sends gamerequest 270 to user 202 by posting game request 270 within one of chatbubbles 222 of message stream 221 a. In the implementation of FIG. 2,game request 270 says “Let us play a game”. Next, user 201 sends user202 the name of the game and the instructions within two more of chatbubbles 222, where the instructions tell user 202 to “Try and hit theapple,” which is illustrated as game object 224. After sending gamerequest 270 to user 202, user 201 then receives game acceptance 271within another one of chat bubbles 222 of message stream 221 a.

Continuing with the implementation of FIG. 2, mobile device 250 includesmessage stream 221 b, which may correspond to message stream 221 aexcept that user 202 has now started playing the shooting game. Asillustrated in message stream 221 b, user 202 first has to shoot chatbubbles 222 which were illustrated in message stream 221 a in order forgame object 224 to be visible. After shooting each of chat bubbles 222,user 202 then has to shoot game object 224 within message stream 221 bto win the game.

FIG. 3 shows a flowchart illustrating a method for generating usergenerated gameplay levels in a chat thread, according to oneimplementation of the present disclosure. The approach and techniqueindicated by flowchart 300 are sufficient to describe at least oneimplementation of the present disclosure, however, other implementationsof the disclosure may utilize approaches and techniques different fromthose shown in flowchart 300. Furthermore, while flowchart 300 isdescribed with respect to FIGS. 1 and 2, the disclosed inventiveconcepts are not intended to be limited by specific features shown anddescribed with respect to FIGS. 1 and 2. Furthermore, with respect tothe method illustrated in FIG. 3, it is noted that certain details andfeatures have been left out of flowchart 300 in order not to obscure thediscussion of inventive features in the present application.

Referring now to flowchart 300 of FIG. 3, flowchart 300 includes (at310) initiating a message exchange session with a remote mobile device,in response to a request received from a user of the mobile device, themessage exchange session displaying a user interface for exchanging textand multimedia messages. For example, processor 111 of mobile device110/210 may execute messaging software application 120 to open a messageexchange session with mobile device 150/250, in response to a requestreceived from user 101/201 of mobile device 110/210, the messageexchange session displaying message stream 121/221 a. As discussedabove, message stream 121/221 a may be used to exchange text andmultimedia messages with mobile device 150/250.

Flowchart 300 further includes (at 320) providing a plurality of gamesfor selection by the user to be played during the message exchangesession and within the user interface for exchanging text and multimediamessages. For example, processor 111 of mobile device 110/210 mayexecute messaging software application 120 to provide games 131 forselection by user 101/201 to be played during the message exchangesession within message stream 121/221 a. As discussed above, user101/201 may be provided with games 131 using game selection 127/227.

Flowchart 300 further includes (at 330) receiving a selection of one ofthe plurality of games by the user after initiating the message exchangesession. For example, processor 111 of mobile device 110/210 may executemessaging software application 120 to receive a selection of one ofgames 131 by user 101/201 after initiating the messaging exchangesession. As discussed above, user 101/201 may select one of games 131using game selection 127/227.

Flowchart 300 further includes (at 340) sending a game request to theremote user device using the user interface for exchanging text andmultimedia messages. For example, processor 111 of mobile device 110/210may execute messaging software application 120 to send game request170/270 to mobile device 150/250 using message stream 121/221 a. Asdiscussed above, game request 170/270 may be sent to mobile device150/250 by posting game request 170/270 within one of chat bubbles122/222.

Flowchart 300 further includes (at 350) receiving a game acceptance fromthe remote user device using the user interface for exchanging text andmultimedia messages in response to sending the game request. Forexample, processor 111 of mobile device 110/210 may execute messagingsoftware application 120 to receive game acceptance 171/271 from mobiledevice 150/250 using message stream 121/221 a in response to sendinggame request 170/270.

Flowchart 300 also includes (at 360) initiating the one of the pluralityof games within the user interface for exchanging text and multimediamessages, wherein a game level for the one of the plurality of games iscreated using chat bubbles within the user interface for exchanging textand multimedia messages. For example, processor 111 of mobile device110/210 may execute messaging software application 120 to initiate theone of games 131 within message stream 121/221 a, wherein a game levelfor the one of games 131 is created using chat bubbles 122/222 withinmessage stream 121/221 a. As discussed above, the game level for the oneof games 131 may further be created using game objects 124/224 selectedfrom objects 132.

As a preliminary note to FIGS. 4A and 4B, FIGS. 4A and 4B illustrateexamples of games that can use the message stream to integrate gamemechanics into the chat conversation. The game mechanics work byproviding a game selection button within the messaging application.Using the game selection button, a first user is able to select a gameto be played. Once a game is selected, a game request is posted withinthe message stream (in a chat bubble), where the game request includes agame acceptance button. When a second user taps on the game acceptancebutton within the message stream, the game will trigger a response.These games may include, but are not limited to, dice rolling games,trivia games, rock-paper-scissors games, time based games, andscratchers games. As such, these games may be played between just twousers using two different mobile devices, or these games may be playedbetween multiple users on multiple mobile devices.

FIG. 4A presents a first example of integrating game mechanics in a chatthread, according to one implementation of the present disclosure. FIG.4A includes mobile device 410, which includes message stream 421 a,keyboard 426, and game selection 427. Message stream 421 a includes chatbubbles 422 (corresponding to messages exchanged between user 401 anduser 402 within message stream 421 a), game request 470, and gameacceptance 471.

With respect to FIG. 4A, it should be noted that user 401, user 402,mobile device 410, message stream 421 a, chat bubbles 422, keyboard 426,game selection 427, game request 470, and game acceptance 471 correspondrespectively to user 101, user 102, mobile device 110, message stream121, chat bubbles 122, keyboard 126, game selection 127, game request170, and game acceptance 171 from FIG. 1. It should further be notedthat only one of chat bubbles 422 within message stream 421 a is labeledfor clarity purposes even though each message exchanged between user 401and user 402 is included within one of chat bubbles 422.

In the implementation of FIG. 4A, user 401 may have used game selection427 to look through the possible games that are available to be playedwithin message stream 421 a and clicked on a game icon that correspondsto a dice rolling game. In response to selecting the dice rolling game,game request 470 has been posted using one of chat bubbles 422 withinmessage stream 421 a along with game acceptance 471, which correspondsto a button that can be used by user 402 to accept game request 470.User 402 may have then seen game request 471 within message stream 421 abeing displayed on his or her own mobile device (not shown), andselected game acceptance 471. In response to user 402 selecting gameacceptance 471, the dice rolling game rolled the dice and selected awinner based on the roll. The dice rolling game further awarded thewinner a prize (illustrated as 100 coins). Finally, user 401 postedanother message within message stream 421 a to play again, which user402 can select to play the dice rolling game a second time.

It should be noted that the implementation of FIG. 4A illustrates atimer within message stream 421 a. In such implementations that includea timer, user 402 may only have a set amount of time to accept gamerequest 470 before game request 470 is cancelled and thus no game iscreated or played. For example, and as illustrated in FIG. 4A, user 402had fifty-eight seconds left to accept game request 470 when user 402selected game acceptance 471.

FIG. 4B presents a second example of integrating game mechanics in achat thread, according to one implementation of the present disclosure.FIG. 4B includes mobile device 410, which includes message stream 421 b,keyboard 426, and game selection 427. Message stream 421 b includes chatbubbles 422 (corresponding to messages exchanged between user 401 anduser 402 within message stream 421 b), game request 470, and gameacceptance 471.

With respect to FIG. 4B, it should be noted that user 401, user 402,mobile device 410, message stream 421 b, chat bubbles 422, keyboard 426,game selection 427, game request 470, and game acceptance 471 correspondrespectively to user 101, user 102, mobile device 110, message stream121, chat bubbles 122, keyboard 126, game selection 127, game request170, and game acceptance 171 from FIG. 1. It should further be notedthat only one of chat bubbles 422 within message stream 421 b is labeledfor clarity purposes even though each message exchanged between user 401and user 402 is included within one of chat bubbles 422.

In the implementation of FIG. 4B, user 401 may now have used gameselection 427 and clicked on a game icon that corresponds to arock-paper-scissors game. In response to selecting therock-paper-scissors game, game request 470 has been posted withinmessage stream 421 b along with icons for a rock, a paper, and scissors.User 401 then uses message stream 421 b being displayed on mobile device410, and user 402 uses message stream 421 b being displayed on his orher own mobile device (not shown), to select either the rock icon, thepaper icon, or the scissors icon within game request 470. After each ofuser 401 and user 402 make a selection, the rock-paper-scissors gamedecides who wins and awards the winner with a prize (illustrated as 100coins).

FIG. 5 shows a flowchart illustrating a method for integrating gamemechanics in a chat thread, according to one implementation of thepresent disclosure. The approach and technique indicated by flowchart500 are sufficient to describe at least one implementation of thepresent disclosure, however, other implementations of the disclosure mayutilize approaches and techniques different from those shown inflowchart 500. Furthermore, while flowchart 500 is described withrespect to FIGS. 1, 4A, and 4B, the disclosed inventive concepts are notintended to be limited by specific features shown and described withrespect to FIGS. 1, 4A, and 4B. Furthermore, with respect to the methodillustrated in FIG. 5, it is noted that certain details and featureshave been left out of flowchart 500 in order not to obscure thediscussion of inventive features in the present application.

Referring now to flowchart 500 of FIG. 5, flowchart 500 includes (at510) initiating a message exchange session with a remote mobile device,in response to a request received from a user of the mobile device, themessage exchange session displaying a user interface for exchanging textand multimedia messages. For example, processor 111 of mobile device110/410 may execute messaging software application 120 to open a messageexchange session with mobile device 150, in response to a requestreceived from user 101/401 of mobile device 110/410, the messageexchange session displaying message stream 121/421 a/ 421 b. Asdiscussed above, message stream 121/421 a/ 421 b may be used to exchangetext and multimedia messages with mobile device 150.

Flowchart 500 further includes (at 520) providing a plurality of gamesfor selection by the user to be played during the message exchangesession and within the user interface for exchanging text and multimediamessages. For example, processor 111 of mobile device 110/410 mayexecute messaging software application 120 to provide games 131 forselection by user 101/401 to be played during the message exchangesession within message stream 121/421 a/ 421 b. As discussed above, user101/401 may be provided with games 131 using game selection 127/427.Games 131 may include, but are not limited to, dice rolling games,trivia games, rock-paper-scissors games, time based games, andscratchers games.

Flowchart 500 further includes (at 530) receiving a selection of one ofthe plurality of games by the user after initiating the message exchangesession. For example, processor 111 of mobile device 110/410 may executemessaging software application 120 to receive a selection of one ofgames 131 by user 101/401 after initiating the messaging exchangesession. As discussed above, user 101/401 may select one of games 131using game selection 127/427.

Flowchart 500 further includes (at 540) sending a game request to theremote user device using the user interface for exchanging text andmultimedia messages, the game request including a chat bubble with agame acceptance button. For example, processor 111 of mobile device110/410 may execute messaging software application 120 to send gamerequest 170/470 to mobile device 150 using message stream 121/421 a/ 421b, game request 170/470 including one of chat bubbles 122/422 with gameacceptance 171/471 button.

Flowchart 500 further includes (at 550) receiving a game acceptance fromthe remote user device using the user interface for exchanging text andmultimedia messages in response to sending the game request. Forexample, processor 111 of mobile device 110/410 may execute messagingsoftware application 120 to receive game acceptance 171/471 from mobiledevice 150 using message stream 121/421 a/ 421 b in response to sendinggame request 170/470. As discussed above, mobile device 110/410 mayreceive game acceptance 171/471 when user 102/402 selects gameacceptance 171/471 button within message stream 121/421 a/ 421 b onmobile device 150.

Flowchart 500 further includes (at 560) playing the one of the pluralityof games in response to receiving the game acceptance and (at 570)determining a winner of the one of the plurality of games. For example,processor 111 of mobile device 110/410 may execute messaging softwareapplication 120 to play the one of games 131 in response to receivinggame acceptance 171/471 and determine a winner for the one of games 131.As discussed above, the one of games 131 may be played within messagestream 121/421 a/ 421 b.

FIG. 6 presents an example of chat message gameplay scripting, accordingto one implementation of the present disclosure. FIG. 6 includes mobiledevice 610, which includes message stream 621, keyboard 626, and gameselection 627. Message stream 621 includes chat bubbles 622(corresponding to messages exchanged between user 601 and user 602within message stream 621), game object 624, and game request 670.

With respect to FIG. 6, it should be noted that user 601, user 602,mobile device 610, message stream 621, chat bubbles 622, game object624, keyboard 626, game selection 627, and game request 670 correspondrespectively to user 101, user 102, mobile device 110, message stream121, chat bubbles 122, one of game objects 124, keyboard 126, gameselection 127, and game request 170 from FIG. 1. It should further benoted that only one of chat bubbles 622 within message stream 621 islabeled for clarity purposes even though each message exchanged betweenuser 601 and user 602 is included within one of chat bubbles 622.

FIG. 6 illustrates an example of a game that can be created within amessage stream that includes chat message gameplay scripting. To playthe game, users are provided with a game trigger that activates a gameobject within the message stream. The users are then able to control thegame object using chat messages posted within the message stream. Thegame trigger can either be a game selection button that is providedwithin the messaging application, or the game trigger can be a certainword or combination of words that is posted within one of the chatmessages. After activating the game object within the message stream,the game object may remain in the message stream for a given amount oftime or until one of the users ends the game.

In the implementation of FIG. 6, user 602 posts game request 670 withinmessage stream 621, which is displayed on mobile device 610 inpossession of user 601. Game request 670 includes the words “PlayRequest” posted within one of chat bubbles 622. In response to user 602posting game request 670 within message stream 621, game object 624 isactivated and appears within message stream 621. Game object 624 isillustrated as an avatar in the implementation of FIG. 6, however, inother implementations, game object 624 may take the form of otherobjects, such as one of objects 132 from FIG. 1.

Continuing with the implementation of FIG. 6, user 601 and user 602 areable to control game object 624 using chat messages posted withinmessage stream 621 after game object 624 has been activated, where chatmessages are represented by chat bubbles 622. For example, user 601posting “Dance” within message stream 621 may cause game object 624 todance. For a second example, user 601 posting a sad face icon withinmessage stream 621 may cause game object 624 to be sad. Finally, for athird example, user 602 posting “Smile and wave” within message stream621 may cause game object 624 to both smile and wave, which isillustrated in FIG. 6.

FIG. 7 shows a flowchart illustrating a method for chat message gameplayscripting, according to one implementation of the present disclosure.The approach and technique indicated by flowchart 700 are sufficient todescribe at least one implementation of the present disclosure, however,other implementations of the disclosure may utilize approaches andtechniques different from those shown in flowchart 700. Furthermore,while flowchart 700 is described with respect to FIGS. 1 and 6, thedisclosed inventive concepts are not intended to be limited by specificfeatures shown and described with respect to FIGS. 1 and 6. Furthermore,with respect to the method illustrated in FIG. 7, it is noted thatcertain details and features have been left out of flowchart 700 inorder not to obscure the discussion of inventive features in the presentapplication.

Referring now to flowchart 700 of FIG. 7, flowchart 700 includes (at710) initiating a message exchange session with a remote mobile device,in response to a request received from a user of the mobile device, themessage exchange session displaying a user interface for exchanging textand multimedia messages. For example, processor 111 of mobile device110/610 may execute messaging software application 120 to open a messageexchange session with mobile device 150, in response to a requestreceived from user 101/601 of mobile device 110/610, the messageexchange session displaying message stream 121/621. As discussed above,message stream 121/621 may be used to exchange text and multimediamessages with mobile device 150.

Flowchart 700 further includes (at 720) providing a plurality of objectsfor selection by the user to be placed within the user interface forexchanging text and multimedia messages. For example, processor ill ofmobile device 110/610 may execute messaging software application 120 toprovide objects 132 and/or avatars 133 for selection by user 101/601 tobe placed within message stream 121/621. As discussed above, objects 132may include, but are not limited to, people, cars, buildings, food,animals, pictures, or movie clips.

Flowchart 700 further includes (at 730) receiving a selection of one ofthe plurality of objects by the user after initiating the messageexchange session. For example, processor 111 of mobile device 110/610may execute messaging software application 120 to receive a selection ofone of objects 132 and/or avatars 133 by user 101/601 after initiatingthe messaging exchange session, where the one of objects 132 and/oravatars 133 selected by user 101/601 may include game object 124/624.

Flowchart 700 further includes (at 740) activating the one of theplurality of objects within the user interface for exchanging text andmultimedia messages. For example, processor 111 of mobile device 110/610may execute messaging software application 120 to activate game object124/624 within message stream 121/621. As illustrated in FIG. 6, gameobject 124/624 includes an avatar.

Flowchart 700 further includes (at 750) controlling the one of theplurality of objects within the user interface for exchanging text andmultimedia messages by posting messages within the user interface forexchanging text and multimedia messages. For example, processor 111 ofmobile device 110/610 may execute messaging software application 120 tocontrol game object 124/624 within message stream 121/621 by postingmessages within message stream 121/621. For example, user 101/601posting “Dance” within message stream 121/621 may cause game object124/624 to dance. For a second example, user 101/601 posting a sad faceicon within message stream 121/621 may cause game object 124/624 to besad. Finally, for a third example, user 102/602 posting “Smile and wave”within message stream 121/621 may cause game object 124/624 to bothsmile and wave, which is illustrated in FIG. 6.

FIG. 8 presents an example of chat based trading with limited timemechanics, according to one implementation of the present disclosure.FIG. 8 includes mobile device 810, which includes message stream 821,keyboard 826, and game selection 827. Message stream 821 includes chatbubbles 822 (corresponding to messages exchanged between user 801 anduser 802 within message stream 821), game object 824 a, game object 824b, game acceptance 871 a and game acceptance 871 b.

With respect to FIG. 8, it should be noted that user 801, user 802,mobile device 810, message stream 821, chat bubbles 822, each of gameobject 824 a and game object 824 b, and each of game acceptance 871 aand game acceptance 871 b correspond respectively to user 101, user 102,mobile device 110, message stream 121, chat bubbles 122, game objects124, and game acceptance 171 from FIG. 1. It should further be notedthat only one of chat bubbles 822 within message stream 821 is labeledfor clarity purposes even though each message exchanged between user 801and user 802 is included within one of chat bubbles 822.

FIG. 8 illustrates an example of a game that can be created within amessage stream that includes trading objects (or items) between userswithin the message stream. For example, a first user that wants to tradea first object would post the first object in the message stream, wherethe post would include a first acceptance button. A second user wouldthen post a second object that he or she wanted to trade in the messagestream, where that post would include a second acceptance button. Thefirst user would then have to accept the second object using the secondacceptance button in the message stream and the second user would haveto accept the first object using the first acceptance button in themessage stream for the trade to occur. If both users do not accept thetrade within a given time limit, or if one of the users declines thetrade by ending the game, then the trade will not occur.

In the implementation of FIG. 8, user 801 first posts game request 470within message stream 821, which is being displayed on mobile device 810in possession of user 801. Game request 870 may be posted in response touser 801 using game selection 827 to select a trading game, or gamerequest 870 may be posted in response to user 801 just posting inmessage stream 821 “Let us trade something”. User 801 then posts gameobject 824 a within message stream 821 for trading with user 802, wheregame object 824 a is posted within one of chat bubbles 822 along withgame acceptance 871 a button. Furthermore, user 801 posts a chat messagein message stream 821 asking user 802 if he or she wants to trade, wherethe chat message says “Alright, how about this”.

In response to the user 801 posting game object 824 a to trade, user 802first notifies user 801 that user 802 is willing to try and make a tradeby posting “Here is mine to trade” within message stream 821. User 802then posts game object 824 b within message stream 821 for trading withuser 801, where game object 824 b is posted within one of chat bubbles822 along with game acceptance 871 b button. In order for a trade to bemade, user 801 must select game acceptance 871 b button and user 802must select game acceptance 871 a button within message stream 821before running out of time. As illustrated in FIG. 8, there is thirtysecond remaining for the trade to be made.

It should be noted that the implementation of FIG. 8 is just one exampleof trading objects within a trading game, however, the presentdisclosure is not limited to the implementation of FIG. 8. For example,in other implementations, user 801 may start the trading game by justposting game object 824 a within message stream 821. In suchimplementations, the posting of game object 824 a within message stream821 would act as game request 870. Furthermore, in otherimplementations, only one of user 801 and user 802 have to accept thetrade to the trade to occur.

FIG. 9 shows a flowchart illustrating a method for chat based tradingwith limited time mechanics, according to one implementation of thepresent disclosure. The approach and technique indicated by flowchart900 are sufficient to describe at least one implementation of thepresent disclosure, however, other implementations of the disclosure mayutilize approaches and techniques different from those shown inflowchart 900. Furthermore, while flowchart 900 is described withrespect to FIGS. 1 and 8, the disclosed inventive concepts are notintended to be limited by specific features shown and described withrespect to FIGS. 1 and 8. Furthermore, with respect to the methodillustrated in FIG. 9, it is noted that certain details and featureshave been left out of flowchart 900 in order not to obscure thediscussion of inventive features in the present application.

Referring now to flowchart 900 of FIG. 9, flowchart 900 includes (at910) initiating a message exchange session with a remote mobile device,in response to a request received from a user of the mobile device, themessage exchange session displaying a user interface for exchanging textand multimedia messages. For example, processor 111 of mobile device110/810 may execute messaging software application 120 to open a messageexchange session with mobile device 150, in response to a requestreceived from user 101/801 of mobile device 110/810, the messageexchange session displaying message stream 121/821. As discussed above,message stream 121/821 may be used to exchange text and multimediamessages with mobile device 150.

Flowchart 900 further includes (at 920) providing a plurality of gamesfor selection by the user to be played during the message exchangesession and within the user interface for exchanging text and multimediamessages. For example, processor 111 of mobile device 110/810 mayexecute messaging software application 120 to provide games 131 forselection by user 101/801 to be played during the message exchangesession within message stream 121/821. As discussed above, user 101/801may be provided with games 131 using game selection 127/827. Games 131may include, but are not limited to, a trading game.

Flowchart 900 further includes (at 930) receiving a selection of one ofthe plurality of games by the user after initiating the message exchangesession. For example, processor 111 of mobile device 110/810 may executemessaging software application 120 to receive a selection of one ofgames 131 by user 101/801 after initiating the messaging exchangesession. As discussed above, user 101/801 may select one of games 131using game selection 127/827.

Flowchart 900 further includes (at 940) sending a game request to theremote mobile device using the user interface for exchanging text andmultimedia messages, the game request including a first object to betraded with the remote mobile device and a first acceptance button. Forexample, processor 111 of mobile device 110/810 may execute messagingsoftware application 120 to send game request 170/870 to mobile device150 using message stream 121/821, game request 170/870 including firstgame object 124/824 a to be traded with mobile device 150 and gameacceptance 171/871 a button. As discussed above, game request 170/870may be sent in one of chat bubbles 122/822.

Flowchart 900 further includes (at 950) receiving a second object fromthe remote mobile device using the user interface for exchanging textand multimedia messages, the second object including a second acceptancebutton. For example, processor 111 of mobile device 110/810 may executemessaging software application 120 to receive second game object 124/824b from mobile device 150 using message stream 121/821, second gameobject 124/824 b including game acceptance 171/871 b button. Asdiscussed above, second game object 124/824 b may be received within oneof chat bubbles 122/822.

Flowchart 900 further includes (at 960) trading the first object for thesecond object using the user interface for exchanging text andmultimedia messages. For example, processor 111 of mobile device 110/810may execute messaging software application 120 to trade first gameobject 124/824 a for second game object 124/824 b using message stream121/821. As discussed above, first game object 124/824 a will be tradedfor second game object 124/824 b when user 101/801 clicks on gameacceptance 171/871 b button and user 102/802 clicks on game acceptance171/871 a button.

FIG. 10 presents an example of a multi modal integrated Avatar emoji,according to one implementation of the present disclosure. FIG. 10includes mobile device 1010, which includes message stream 1021,keyboard 1026, and game selection 1027. Message stream 1021 includesavatar emoji 1040, which includes avatars 1033. Message stream 1021further includes user input 1025 a and user input 1025 b, which arecollectively referred to as user input 1025. With respect to FIG. 10, itshould be noted that mobile device 1010, message stream 1021, user input1025, keyboard 1026, game selection 1027, and avatars 1033 correspondrespectively to mobile device 1010, message stream 121, user input 125,keyboard 126, game selection 127, and avatars 133 from FIG. 1.

In the implementation of FIG. 10, a first user (such as user 101 fromFIG. 1) may be using mobile device 1010 to exchange text and multimediamessages with a second user on another mobile device (such as user 102on mobile device 150 from FIG. 1) within message stream 1021. The firstuser may want to express how he or she feels within message stream 1021.In order to express his or her feelings, the first user may open a multimodal integrated avatar emoji, such as avatar emoji 1040 of FIG. 10. Forexample, and discussed above, keyboard 1026 may include a specialkeyboard that can be used to type special figures, such as differentemotional faces or objects. As such, the first user may have openedavatar emoji 1040 using keyboard 1026.

As illustrated in FIG. 10, avatar emoji 1040 includes avatars 1033, witheach of avatars 1033 including a different emotional expression. Forexample, the avatars in the first column include scared expressions, theavatars in the second column include happy expressions, the avatars inthe third column include sad expressions, and the avatars in the fourthcolumn include angry expressions. Furthermore, the intensity level foravatars 1033 changes within each of the rows. For example, theexpressions of the avatars in the first row include the highest level ofintensity for each expression, and the avatars in the fourth row includethe lower level of intensity for each expression.

Avatar emoji 1040 makes it easy for the user of mobile device 1010 toquickly select the one of avatars 1033 that best fits his or heremotional mood. In order to select one of avatars 1033 within avataremoji 1040, the user swipes horizontally using user input 1025 a(represented by the line that includes left and right arrows) to selectwhich emotion the user is feeling. The user may then swipe verticallyusing user input 1025 b (represented by the line that includes up anddown arrows) to select the level of intensity for the selected emotion.After an avatar has been selected, mobile device 1010 may post theselected avatar message stream 1021 to represent the current emotion ofthe user.

It should be noted that the implementation of FIG. 10 only illustratesavatar emoji 1040 as including avatars 1033 representing differentemotions, however, the present disclosure is not limited to theimplementation of FIG. 10. In other implementations, avatars mayrepresent something other than emotions. For example, the avatars mayeach represent a different sports team or sporting event. In such anexample, each avatar may be wearing sporting gear from a specific sportsteam or sporting event. Still in other implementations, avatar emoji1040 may include objects other than avatars, such as objects 132 fromFIG. 1. In such, implementations, the user may select between differentobjects 132 using a similar method as discussed above.

FIG. 11 shows a flowchart illustrating a method for using a multi modalintegrated Avatar emoji, according to one implementation of the presentdisclosure. The approach and technique indicated by flowchart 1100 aresufficient to describe at least one implementation of the presentdisclosure, however, other implementations of the disclosure may utilizeapproaches and techniques different from those shown in flowchart 1100.Furthermore, while flowchart 1100 is described with respect to FIGS. 1and 10, the disclosed inventive concepts are not intended to be limitedby specific features shown and described with respect to FIGS. 1 and 10.Furthermore, with respect to the method illustrated in FIG. 11, it isnoted that certain details and features have been left out of flowchart1100 in order not to obscure the discussion of inventive features in thepresent application.

Referring now to flowchart 1100 of FIG. 11, flowchart 1100 includes (at1110) initiating a message exchange session with a remote mobile device,in response to a request received from a user of the mobile device, themessage exchange session displaying a user interface for exchanging textand multimedia messages. For example, processor 111 of mobile device110/1010 may execute messaging software application 120 to open amessage exchange session with mobile device 150, in response to arequest received from user 101 of mobile device 110/1010, the messageexchange session displaying message stream 121/1021. As discussed above,message stream 121/1021 may be used to exchange text and multimediamessages with mobile device 150.

Flowchart 1100 further includes (at 1120) providing a modal within theuser interface for exchanging text and multimedia messages, the modalincluding a plurality of avatars representing a plurality of emotionalfeelings. For example, processor 111 of mobile device 110/1010 mayexecute messaging software application 120 to open avatar emoji 1040within message stream 121/1021, avatar emoji 1040 including avatars133/1033 representing a plurality of emotional feelings. As discussedabove, the avatars in the first column of avatar emoji 1040 includescared expressions, the avatars in the second column of avatar emoji1040 include happy expressions, the avatars in the third column ofavatar emoji 1040 include sad expressions, and the avatars in the fourthcolumn of avatar emoji 1040 include angry expressions.

Flowchart 1100 further includes (at 1130) receiving a selection from theuser for one of the plurality of avatars, wherein the user selects theone of the plurality of avatars by swiping horizontally to choose one ofthe plurality of emotional feelings and swiping vertically to choose oneof a plurality of intensity levels for the one of the plurality ofemotional feelings. For example, processor 111 of mobile device 110/1010may execute messaging software application 120 to receive a selectionfrom user 101 for one of avatars 133/1033, wherein user 101 selects theone of avatars 133/1033 by using user input 125/125 a to choose one ofthe plurality of emotional feelings and user input 125/125 b to chooseone of a plurality of intensity levels for the one of the plurality ofemotional feelings.

Flowchart 1100 further includes (at 1140) sending the one of theplurality of avatars to the remote mobile device using the userinterface for exchanging text and multimedia messages. For example,processor 111 of mobile device 110/1010 may execute messaging softwareapplication 120 to send the one of avatars 133/1033 to mobile device 150using message stream 121/1021.

From the above description it is manifest that various techniques can beused for implementing the concepts described in the present applicationwithout departing from the scope of those concepts. Moreover, while theconcepts have been described with specific reference to certainimplementations, a person of ordinary skill in the art would recognizethat changes can be made in form and detail without departing from thescope of those concepts. As such, the described implementations are tobe considered in all respects as illustrative and not restrictive. Itshould also be understood that the present application is not limited tothe particular implementations described above, but many rearrangements,modifications, and substitutions are possible without departing from thescope of the present disclosure.

What is claimed is:
 1. A mobile device comprising: a memory storing atext and multimedia messaging software application; and a processorconfigured to execute the text and multimedia messaging softwareapplication to: initiate a message exchange session with a remote mobiledevice, in response to a request received from a user of the mobiledevice, the message exchange session displaying a user interface forexchanging text and multimedia messages; provide a plurality of gamesfor selection by the user to be played during the message exchangesession and within the user interface for exchanging text and multimediamessages; receive a selection of one of the plurality of games by theuser after initiating the message exchange session; and initiate the oneof the plurality of games for playing within the user interface forexchanging text and multimedia messages.
 2. The mobile device of claim1, wherein before the initiating of the one of the plurality of games,the processor is further configured to execute the text and multimediamessaging software application to: send a game request to the remoteuser device using the user interface for exchanging text and multimediamessages.
 3. The mobile device of claim 2, wherein before the initiatingof the one of the plurality of games, the processor is furtherconfigured to execute the text and multimedia messaging softwareapplication to: receive a game acceptance from the remote user deviceusing the user interface for exchanging text and multimedia messages inresponse to the sending of the game request.
 4. The mobile device ofclaim 1, wherein the user plays the one of the plurality of games usingthe user interface for exchanging text and multimedia messages.
 5. Themobile device of claim 1, wherein the processor is further configured toexecute the text and multimedia messaging software application to:generate a game level for the one of the plurality of games within theuser interface for exchanging text and multimedia messages.
 6. Themobile device of claim 5, wherein the game level is generated using textbubbles, the text bubbles used to display messages exchanged with theremote mobile device during the message exchange session and within theuser interface for exchanging text and multimedia messages.
 7. Themobile device of claim 1, wherein the processor is further configured toexecute the text and multimedia messaging software application to:provide a plurality of objects for selection by the user to be usedduring the playing of the one of the plurality of games; receive aselection of one of the plurality of objects by the user; and post theone of the plurality of objects within the user interface for exchangingtext and multimedia messages during the playing of the game.
 8. Themobile device of claim 7, wherein the one of the plurality of gamesincludes shooting the one of the plurality of objects using the userinterface for exchanging text and multimedia messages.
 9. The mobiledevice of claim 1, wherein the processor is further configured toexecute the text and multimedia software application to: receive a userinput from the user during the playing of the one of the plurality ofgames, the user input corresponding to a move made by the user for theone of the plurality of games; and post the move within the userinterface for exchanging text and multimedia messages.
 10. The mobiledevice of claim 1, wherein the one of the plurality of games isdisplayed simultaneously with messages exchanged with the remote mobiledevice during the message exchange session and within the user interfacefor exchanging text and multimedia messages.
 11. A method for using amobile device to generate a game during a message exchange session witha remote mobile device, the method comprising: initiating the messageexchange session with the remote mobile device, in response to a requestreceived from a user of the mobile device, the message exchange sessiondisplaying a user interface for exchanging text and multimedia messages;providing a plurality of games for selection by the user to be playedduring the message exchange session and within the user interface forexchanging text and multimedia messages; receive a selection of one ofthe plurality of games by the user after initiating the message exchangesession; and initiate the one of the plurality of games for playingwithin the user interface for exchanging text and multimedia messages.12. The method of claim 11 further comprising: sending a game request tothe remote user device using the user interface for exchanging text andmultimedia messages.
 13. The method of claim 12 further comprising:receiving a game acceptance from the remote user device using the userinterface for exchanging text and multimedia messages in response to thesending of the game request.
 14. The method of claim 11, wherein theuser plays the one of the plurality of games using the user interfacefor exchanging text and multimedia messages.
 15. The method of claim 11further comprising: generating a game level for the one of the pluralityof games within the user interface for exchanging text and multimediamessages.
 16. The method of claim 15, wherein the game level isgenerated using text bubbles, the text bubbles used to display messagesexchanged with the remote mobile device during the exchange session andwithin the user interface for exchanging text and multimedia messages.17. The method of claim 11 further comprising: providing a plurality ofobjects for selection by the user to be used during the playing of theone of the plurality of games; receiving a selection of one of theplurality of objects by the user; and posting the one of the pluralityof objects within the user interface for exchanging text and multimediamessages during the playing of the game.
 18. The method of claim 17,wherein the one of the plurality of games includes shooting the one ofthe plurality of objects using the user interface for exchanging textand multimedia messages.
 19. The method of claim 11 further comprising:receiving a user input from the user during the playing of the one ofthe plurality of games, the user input corresponding to a move made bythe user for the one of the plurality of games; and posting the movewithin the user interface for exchanging text and multimedia messages.20. The method of claim 11, wherein the one of the plurality of games isdisplayed simultaneously with messages exchanged with the remote mobiledevice during the exchange session and within the user interface forexchanging text and multimedia messages.